🔍 Problem

• The docs only describe load_zmq and save_zmq, which models the old byte-oriented API.
• The upcoming executor work introduces event-oriented ZeroMQ operators with separate connect and bind modes.
• The old docs also overstate the role of monitor on the read side.

🛠️ Solution

• Add reference pages for from_zmq, accept_zmq, to_zmq, and serve_zmq.
• Update the ZeroMQ integration page to describe the new executor operators.
• Keep load_zmq and save_zmq documented as the legacy-executor path instead of marking them deprecated.
• Document prefix as the PUB/SUB routing primitive and scope monitor to the publishing side.

💬 Review

• Check whether the documented split between connect and bind matches the intended TQL surface.
• Check whether encoding on write and nested read_* pipelines on read are described precisely enough.
• Check that the rollout wording does not imply load_zmq and save_zmq are deprecated before the new executor becomes the default.

Functional PRs

• Add new ZeroMQ operators tenzir#5999